Asset Transformation API

1.0.x
(0 reviews)

Best Practices

Fault Handling
This section lists some helpful tips about how client application can resolve faults and common issues they may encounter while making requests against the API
```

  1. Most errors can be resolved by allowing short pause between requests.

  2. Implementing retry logic.

  3. Implementing failure logic on multiple retries.




**Message Payload Size management**



Using GZIP compression is one way of achieving this



- it increases the speed of data requests















- Easily implemented by adding HTTP headers





**Randomize Refresh Rates**



Add some randomization to the consumer application refresh times.



**Content Negotiation**



It is important to specify the content-type required for the API call responses, for example set your content-type: header to application/json



[Currently only JSON content-types are supported].





**Persistent Connections**



It's recommended to use persistent connections as they improve the performance by removing the overhead of creating new connections.

A consideration to take into account is to make sure that the client re-uses its connections to prevent a situation where they are exhausted.







It is suggested to use connection pools where possible.

Reviews